BBS in a Box 4/BBS in a Box - Macintosh - Volume IV (January 1992) (BBS in a Box).iso/Files/Tele/M/MAUGForms

Text File | 1989-09-03 | 27.0 KB | 513 lines | [TEXT/MACA]

HELPME.txt

A GUIDE TO USING MAUG(tm) FORUMS

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Welcome to the forums of MAUG.
MAUG stands for (M)icroNetworked (A)pple (U)sers (G)roup, and was coined
by the founder and chief Sysop, Neil Shapiro. MAUG is a trademark of
MCU, Inc.

While the forums may initially seem a bit intimidating, the information in
this file will help you to put all the pieces together, and feel right at
home. You'll be able to take advantage of the tremendous resources of MAUG,
the extensive data libraries, the knowledge of the participants on the
message boards, the camaraderie of the real time conference: all will be at
your fingertips.

Using the forum is easy. The message base can be mastered quickly and
using the data libraries is also quite easy (the adoption of a standard for
Macintosh telecommunications, called MacBinary, has simplified use of the
data libraries immensely).

This help file is organized as follows:

(1) Finding your way around MAUG.

(2) Finding your way around the data libraries.

(3) Downloading files.

(4) Uploading files.

(5) A few words on messages.

This file is recommend reading for all users of MAUG, and spending a few
minutes to understand the information here will make the MAUG experience
fulfilling, instead of frustrating. Be sure to save this file in your
archives. You may not grasp all the information presented here right
now, but after a little experience in the data libraries and message
sections, it's likely you'll find a second (or third) reading to be of
great benefit to you.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(1) Finding your way around MAUG.

MAUG is big place, with a number of different forums which will interest
you. Each forum has a particular slant: business, productivity,
programming, users' groups, arts and entertainment, the Apple ][ and ///
computers, HyperCard, ....

All the forums have a consistent interface; they all look and work in
the same manner. In each forum you can change certain user options. When
you first join a forum you will be in "menu mode." Most users prefer to be
in "command mode", especially after they have a little experience on the
forums. Often, even beginners prefer "command mode", because they can
type a question mark ("?") or the word "HELP" at any "command mode"
prompt, and get more information.

To change to command mode, type OP (for options) at any "Function:" or
menu prompt. Observe the menu of choices available to you, and set
"USE MENUS" to "OFF." When changed, type return, and when given the choice,
type P to make your changes permanent. If you find you're not ready for
"command mode" yet, use the OP command to get back into the options mode,
and set "USE MENUS" back to ON.

The text of this document assumes you are in "command mode". If you aren't,
don't be too concerned, this information is valuable in either mode, and
almost every "command mode" command is also available while you're in the
"menu mode".

In all of the MAUG forums, you can type LN at a "Function:" prompt, and
be given a list of the data libraries for that forum. You might wish to
visit all the forums interesting to you, do an LN in each forum, and then
make yourself a reference listing of the data library names. Similarly, you
can type SN to get a list of the subtopic names for a forum.

To enter a data library, type DLx, where x is the number of the data
library you want. If you don't know what "x" to use, just type DL, and
you'll be given a list of choices.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(2) Finding your way around the data libraries.

When you've entered a data library  you might know exactly what you want
(perhaps you saw the name in the data library bulletin, which is updated
daily), or you might just be browsing, looking for interesting items.

There are a number of commands that will be of value to you. A full set of
help information can be obtained by typing "?" at any data library prompt,
and then taking advantage of the choices presented to you.

The command you'll probably want to use most often is BRO (for browse).
With BRO (you can abbreviate any "command mode" command to three
characters) you have the option of using several modifiers. Some sample
uses are as follows.

     BRO MYFILE.BIN      -- looks for the specific file named MYFILE.BIN.
                            If there happens to be two files of the same
                            name, uploaded by different individuals, you
                            will be shown both.

     BRO [77777,777]     -- looks for files uploaded by the individual
                            whose CompuServe ID# is 77777,777

     BRO/KEY: COLOR      -- looks for all files that have a "keyword"
                            of COLOR

     BRO/AGE: 9          -- looks for all files that are 9 days old or less

As mentioned, there are many other possible commands and command
combinations and they may be researched via the help files. One handy
command that is CAT/DES, which will give you a CATalog of the DEScriptions
of all the files in a data library. Remember, to abort a listing that goes
on longer than you'd like, type control-P (control characters are generated
differently by different telecom programs, the actual key strokes could be
control-P, option-P or command-P). Some of the larger MAUG data libraries
have a LOT of files, and a CAT/DES of a large library can take HOURS.
Because of this, we often have compressed listings available; ask the Sysop
(by leaving a message) if there are any compressed data library listings
available, if you're interested.

If you have trouble locating a file, you are welcome to leave a note to the
forum Sysop or to "All." Help will be provided.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(3) Downloading files.

Since the evolution of the MacBinary standard, downloading files has become
quite simple, and almost all current telecommunication software supports
the MacBinary standard.

If you don't have a terminal program which supports MacBinary, the kindest
thing you can do for yourself is to get one that does. It will simplify
everything immensely, and use of MacBinary is also faster (and therefore
less expensive) than using the older methods of downloading.

Detailed information about the MacBinary standard is available in the MAUG
forum called Apple Developers. Use the command GO APPDEV to get there.

A free, public domain terminal program called FREETERM supports MacBinary,
and is available in the telecommunications data library of the Macintosh
Productivity Forum. Use the command GO MACPRO to get there.

If you don't have MacBinary, or if you make a mistake and download without
MacBinary turned on, it may be possible to salvage your downloaded files.
This will be discussed a little later.

For more background information on MacBinary and BINHEX, please refer to
files in both APPDEV and MACPRO (in the telecommunications data library).

MacBinary is compatible with a number of telecommunication protocols,
including XMODEM, CIS A, CIS B, KERMIT and others. The most commonly used
protocol seems to be XMODEM, so this help file will assume you are going
to use XMODEM. The principles given here are applicable to all the various
protocols.

Now, suppose you have BROwsed for, and located, a file in one of the data
libraries, and wish to obtain it. You're at a prompt labeled "Disposition:"
The file may or not be in MacBinary format (MacBinary files will have
" /binary" following their names). It doesn't matter, though, MacBinary is
smart enough to deal with files of any existing type.

Type DOW to start the download proceedings. (When you want to get a file
from CompuServe, you DOWNLOAD it; when you want to send a file to
CompuServe, you UPLOAD it.) After you type DOW, you'll be presented with a
list of protocols to choose from. Pick XMODEM. (If you're using CIS B,
this will be handled transparently by your telecom program and CompuServe,
and you won't have to choose a protocol).

CompuServe will then tell you that it is sending the file, and to press
<return> when the transfer is complete (the message might not be exactly
this, but the intent is clear). At this point, tell your telecom program to
receive a file, using XModem with the MacBinary option enabled. The exact
means of doing this varies from program to program, but should be documented
in your owner's manual. In most instances it simply involves making a choice
of something akin to "Receive File" from the File Menu.

Your telecom program will inform you of the progress of the download. If
all goes well the document will appear on your disk, ready for use.

Several problems could have occurred, though.

-- your telecom program "timed out" at some point. Most easily fixed by
   using a direct CompuServe node, and avoiding TELENET or TYMNET for
   downloading. Sometimes ameliorated by setting "long time outs" in your
   program. For overseas callers there are help files specific for
   improving the "time out" situation. They can be located with a
   BRO/KEY: HELP in this data library.

-- an unexpected error of unknown type occurred. Well, maybe it was an
   excessively noisy phone line. In any case, if an error occurs, always
   exit the forum and reenter before trying to download again. Otherwise
   the error can occur again, at exactly the same place (there is an
   obscure bug which tends to cause errors to repeat).

-- everything seemed fine, but you forgot to set your terminal program for
   MacBinary. Don't worry, your file can be salvaged (as discussed below).

-- everything seemed fine, you used MacBinary appropriately, but got a TEXT
   document. First, consider that the file might really have been TEXT.
   MacBinary is smart about this: if the file _is_ TEXT, you _get_ TEXT. If
   the file was not supposed to be text, the most common cause of the
   problem is that you were running under MultiFinder and downloaded into
   either the system folder or into an open folder. To avoid the problem,
   download only to closed folders other than the system folder when using
   MultiFinder. To repair the damage that has already occurred, use Apple
   Computer's ResEdit to set the file's TYPE and CREATOR attributes to the
   correct ones (ask for help on the message board if you need it).


Don't forget that you can read TEXT files (sometimes called ASCII files)
with any word processing program (some programs require a conversion step).
Just because you can't double click on the document and get your word
processor to open (the dreaded "Application can't be found" dialog),
doesn't mean you can't read it. If the file is supposed to be a text file,
(like this document, for example), you can probably read it by launching
your word processor first, and then using the OPEN command in your word
processor to open the document.

If the file you downloaded was not supposed to be a TEXT file, and you
didn't make the "MultiFinder open folder" mistake, and you really had
MacBinary turned on, the file may be very old, from before the establishment
of the MacBinary standard. You can expect this to occur if:

          -- The file name ends in .HEX, .HCX or .HQX
          -- The file description suggests that it needs conversion by
             BINHEX, and it's dated many years ago.

When you get such a file you need to avail yourself of a conversion utility
called BINHEX version 5. BINHEX is easy to use, simply run it and choose
"Download to Application" from the File Menu. You'll then be given a
standard dialog box and can proceed easily from that point. BINHEX can be
obtained from the telecommunications data library of MACPRO. If your
terminal program doesn't support MacBinary, you'll have to take special
steps to "bootstrap" into BinHex. You'll want to read the help called
BINHEX.HLP from DL1 of MACPRO and possibly download the file BINHEX.BIN
from the MACPRO telecom data library.

As a final complicating factor, many files on CompuServe have been
especially pre-processed by their uploaders. Two commonly used
pre-processing utilities are Packit and Stuffit. These programs have two
features of importance: they can group a number of related files into a
single file; and, they can compress the files into smaller packages, to
reduce uploading and downloading time.

Packit files are characterized by a .PIT suffix. Stuffit files are
characterized by a .SIT suffix. After you've logged off CompuServe you must
run the appropriate program and "unstuff" or "unpack" your download. Packit
and Stuffit are both in the telecom DL of MACPRO, and are also placed in
several of the data libraries designated for SIG Business (SIG is the old
word for forum and means "special interest group").

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(4) Uploading files.

If you've downloaded, you'll find uploading easy. You do it just like
downloading, except backwards. Enter the data library appropriate for the
file you are uploading. Type UPL. A number of short dialogs will then occur;
CompuServe will ask you what protocol you want to use (most of the time the
answer to this one is same as you answered when you were downloading,
XMODEM). If your terminal program supports CIS B protocol, you won't get
asked these questions. Then you'll be asked what the filetype is, either
binary or ascii, or if it's a GIF file. Unless you are sending a plain,
unformatted, styleless text document, you should select BINARY. If your
terminal program supports sending special CompuServe GIF graphics files, it
probably also supports CIS B protocol, so you should never answer the file
type question with GIF unless you really know what you're doing. CompuServe
will then ask you for a name for the file. You can use most any name you
want, but there are some rules that CompuServe requires:

   -- filenames can have no more than 6 characters, followed by a period
      and 3 more characters.

   -- the first six letters should be logically derived from the real
      filename of the file you are uploading; include only letters and
      numbers, with no unusual symbols

   -- a period or dot follows these first six letters

   -- a three letter suffix follows. The suffix should be chosen thusly:
     --if the file is text format, and may be read online, append TXT
     --if the file is MacBinary format, append BIN
     --if the file is MacBinary format, compressed with Packit, append PIT
     --if the file is MacBinary format, compressed with Stuffit, append SIT

(Now that you know about the filename, I can tell you that you can just
type "UPL filnam.ext" instead of typing "UPL" and then the filename...)

After all this has been determined, CompuServe will inform you of its
readiness to receive a file. Choose Send File from your telecommunication
program's File Menu (or use whatever is most appropriate according to your
manual). Make sure MacBinary is enabled (when appropriate), or the upload
will be wasted.

Your telecom program will inform you of the progress of the upload. When
finished, type a return, and wait a moment while CompuServe does some
housekeeping. You will then be prompted for some very vital information.

First, CompuServe will request a description (500 characters or less)
of the file you just uploaded.

In your description you should state briefly what the file is, what it
does, what version it is, what other software must be used with it, what
hardware is required and anything else you feel is important. If the file is
compressed with a compression utility it is ABSOLUTELY MANDATORY that you
state this in the description. If the file is a demo, or a limited use file,
or shareware, it is ABSOLUTELY MANDATORY that you state this in the
description.

It is helpful to prepare descriptions off-line before uploading. It is
helpful to browsers if you are accurate and informative. Users of the data
libraries become rightfully infuriated if your description is misleading or
omits vital information.

Second, after getting the file description CompuServe will prompt you for
a list of keywords.

For keywords, use only letters and numbers, no special symbols. These words
will be used by people browsing in the data library to find your file. So
spend some time thinking of appropriate words, and come up with a good list
of about a half dozen. Consider the effect of alternate spellings and
plurals. Consider the effect of compound words. You should almost always
include the real filename in the keywords if the CompuServe filename is
not the same.

As an example, suppose you have write a program that displays color
pictures on the Macintosh, and you call it "ColorLook". You might wish to
use keywords of COLOR COLOUR COLORLOOK LOOK GRAPHIC GRAPHICS PICT PICTURE
PICTURES.

After completing entry of the keywords CompuServe will ask you if
everything is correct. Make changes if necessary, or just tell CompuServe
"OK." Your uploaded file will then be held temporarily in a private area,
pending the nightly merging of new files into the data library.


If you try to upload a file and CompuServe tells you there is no room,
please feel free to upload the file to another data library here (if a
forum has a DL0 that is a good place, otherwise DL1). In your description
simply add a phrase, "Please put this in DL6," or something similar, to let
the Sysop know to move it. It is also helpful if you drop a brief message on
the board to the Sysop stating the lack of room in your chosen data library.


If you upload a file that has the same name as a file you have previously
uploaded, the new file will overwrite (annihilate) the old file. You can do
this purposefully, if you are uploading a new version of an old program. You
can do this inadvertently, too (but CompuServe does warn you that it will
happen, and you have a chance to back out). If you erase an old file
inadvertently, and don't tell the Sysop in time for your ERAse command to be
undone, there is absolutely nothing that can be done to salvage it. If you
goof and ERAse one of your files, a timely note to the Sysop MAY save it.


If you upload a new file with a different name, and wish to have an old
version deleted, please take care of this detail yourself. Find your old
file, and type ERA (for erase) at the disposition prompt. You can erase only
files under your own ID#, you can't erase the files of other people. Please
do take care of seemingly small issues like this. Users of the data library
can harbor justifiable resentment if they download a file only to discover
that a newer version was already available.


If you come to realize that a description or a set of keywords isn't ideal
for your program, you can change them at your leisure. Simply locate the
file you need to adjust, and at the disposition prompt type CHA (for
change). You'll be able to make whatever changes you need. Note that you
can't use the CHAnge command until the Sysop MERges the files, so if you
upload a file, and want to change the Keywords or Description, you'll have
to wait until the next day, when the file becomes available. If you have
a real emergency (whatever that means) about the content of your files
description, and REALLY need it changed before it ever shows up, drop a
note to the Sysop in that forum.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(5) A few words on messages.

After a bit of practice on the MAUG boards, you will probably find that it
is most efficient to be in "command mode" as described earlier. This
discussion also assumes you are in command mode.

There are a few commands that will help you read messages of interest to
you.

RM  -- read marked. Allows you to read messages that were left for you,
without going through any other messages. A message will be marked for your
reading if the person who left the message included your CompuServe
identification number. If they didn't, it won't be. Remember this when you
are leaving messages: include the person's ID (also called a "ppn").

RS  -- read search. Allows you to search for messages according to certain
criteria. Example 1: rs;f;Shapiro;n. Translation: search for messages From
anyone named Shapiro, but only if the messages are New (since last you used
the forum). Example 2: rs;t;Steinberg;0. Translation: search for message To
anyone named Steinberg beginning at message number zero (this trick is great
for finding out someone's ID, if that person is on the board fairly
reliably). Example 3: rs;s;Castle;3000. Translation: search for any message
in which the word Castle appears in the subject field, beginning at message
number 3000.

RE  -- reply. If you've read a message, and are at the disposition prompt
immediately after that message, RE will automatically hook your response to
that message. That is, your response will be addressed to the originator of
the message (this is usually the best way to get involved with an ongoing
conversation). The RE command will automatically use the same Subject, will
automatically include the person's CompuServe ID#, and will keep your
message in the proper "thread" order with the discussion going on. When you
(and others) read messages in "thread order", you get to see all the replies
to each message without reading messages that were left in between. It is a
common error to respond to a responder, instead of the person you meant. The
RP (read previous (message)) or RT (read the whole "thread" or group of
messages on this topic, starting at the beginning) will take you "back up
the thread". When you are at a "Function:" prompt, the RE command is a bit
different. Since CompuServe doesn't know what message you want to REply to,
it will ask you for a message number.  Use the REply command from the
Function: prompt only if you already know the message number of the message
you want to reply to. (And since you already know the message number, you
might as well use the "shortcut" syntax of= RE;xxxx, where xxxx is the
message number to which you wish to reply).

RI  -- read individual. The whole syntax is RI;xxxx, with xxxx being the
individual message you wish to read.

UA  -- use address. This works like reply, after reading a message, except
it allows you to choose a new subject for the message, and a new message
subtopic. Use this command when you want to talk to someone, but the topic
of your note is inappropriate for the message title or the message
subtopic.

RTN -- read thread new. That means read all the new messages in the
subtopics you've selected, in the order of the thread (i.e., replies follow
the messages to which they reply).

SM  -- stop mode. This command is handy when doing an RTN. You can turn the
stops off, so you don't have to keep typing return. SM;N is never stop,
SM;A is always stop, SM;T is only stop when the message is to you.

SS  -- set subtopics. You might use SS;A to ready everything for reading
the entire message board. Or you could use ss;0,3,6,9 to ready yourself for
reading messages just from those subtopics.

Commands can be strung altogether, too. As an example, you might wish to
type something like: sm;t;ss;1,13;rtn. The commands are taken in order...
stop only if a message is to you, set the subtopics to just 1 and 13, and
then read the new messages in thread order. It might seem a bit complicated,
but will become second nature after a little practice. If things seem to be
running out of control and you can't escape, type control-P to get back up
to the "Function:" prompt. Or, if all else fails, try control-C.

Remember, output can be temporarily halted from CompuServe with control-S,
and restarted with control-Q (as mentioned elsewhere, control characters
are generated from the keyboard in different ways from different programs,
with command-S, control-S, option-S... all being possibilities for your
setup).


L   -- leave a message. You will be prompted for several items of
information as you progress through the message. The important items the
message recipient (include the ID#!!), the message topic (try to be
somewhat informational), the message subtopic (please use the appropriate
subtopic, in the correct forum) and the message itself. Messages get the
best response when they observe the following conventions:

       -- the message uses mixed upper and lower case letters.

       -- the message gives the reader enough information.

       -- the message, if long, has a line of white space between
          paragraphs (this helps immensely on the legibility).

       -- the message is left once and only once. Regular readers of the
          message bases of multiple MAUG forums get upset if they read
          the same message over and over again. If you don't get a response
          to a message, try again in a day or so. If you leave the same
          message in 5 sections of the same forum, the Sysop will delete
          4 of them, and probably yell at you.

S   -- store. Store a message, that is. There are other store options (like
SU for store unformatted), but it is suggested you not use the SU option
unless you are sure you wish to use it. S generally does a better job. SP
(store private) is not enabled in MAUG. The whole of the board (except
for a tiny portion of it that the Sysops use for handling certain very
technical matters) is public (and you may jump into any of these public
conversations at any time; after all, it is your unique view that may prove
to be the one that really needs to be heard).

You may have noticed that the word "Function:" is usually spelled
Functi*n in any messages left on the forums. This is simply a matter of
kindness and consideration. It seems some telecommunications programs, when
running auto-pilots, react badly to the correct spelling of the word. So,
while it isn't a rule, we try not use it, so that individuals using these
telecom programs won't have unexpected results.


Many other commands are available in the message area, but the ones
mentioned here will solve most of your needs. Typing a "?" at the forum
"Function:" prompt will provide you with help on the other commands.
Remember, you can always leave a message to Sysop, and someone will try
to help.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Well, that's it! We sincerely hope that reading this file will contribute
to your pleasure in using the forums of MAUG. If you found any aspects of
this discussion inadequate, or if you encounter problems not addressed in
this document, please let us know.  --the MAUG (tm) sysop staff